Computer-based systems with tools designed for real-time reconfiguring a plurality of distinct databases and methods of use thereof

ABSTRACT

Systems and methods associated with providing user interfaces and back-end processing features for transferring recurring charges from a first account to a second account are disclosed. In one embodiment, an exemplary method may comprise receiving a request from a user to transfer recurring charges from a first account to a second account, generating a first user interface that enables the user to provide account information comprised of a plurality of statements and/or account credentials associated with the first account, determining at least one recurring charge of the first account using the account information, generating a second user interface to display the at least one recurring charge and prompt the user to submit merchant-related credentials associated with the at least one recurring charge, transferring the merchant-related credentials, the at least one recurring charge from the first account to the second account.

COPYRIGHT NOTICE

A portion of the disclosure of this patent document contains materialthat is subject to copyright protection. The copyright owner has noobjection to the facsimile reproduction by anyone of the patent documentor the patent disclosure, as it appears in the Patent and TrademarkOffice patent files or records, but otherwise reserves all copyrightrights whatsoever. The following notice applies to the software and dataas described below and in drawings that form a part of this document:Copyright, Capital One Services, LLC., All Rights Reserved.

FIELD OF TECHNOLOGY

The present disclosure generally relates to computer-based systems withtools designed for real-time reconfiguring a plurality of distinctdatabases and methods of use thereof.

BACKGROUND OF TECHNOLOGY

A computer network platform or system may include a group of computers(e.g., clients, servers, smart routers, etc.) and other computinghardware devices that are linked together through one or morecommunication channels to facilitate communication, account managementand/or electronic handling.

SUMMARY OF DESCRIBED SUBJECT MATTER

In some embodiments, the present disclosure provides various exemplarytechnically improved computer-implemented methods for transferringrecurring charges from a first account to a second account, including amethod having steps such as:

receiving, by at least one computing processor, a request from a user totransfer recurring charges from a first account of a first financialinstitution to a second account of a second financial institution;

generating, by the at least one computing processor, a first userinterface that enables the user to provide account informationassociated with first account, wherein the account information comprises(i) a plurality of statements associated with the first account, (ii)account credentials associated with the first account, or both (i) and(ii);

determining, by the at least one computing processor and using theaccount information, at least one recurring charge of the first account;

generating, by the at least one computing processor, a second userinterface that is configured to:

-   -   (i) display to the user the at least one recurring charge, and    -   (ii) prompt the user to submit merchant-related credentials        associated with the at least one recurring charge; and

transferring, by the at least one computing processor and using themerchant-related credentials, the at least one recurring charge from thefirst account to the second account.

In some embodiments, the present disclosure also provides exemplarytechnically improved computer-based systems and computer-readable media,including media implemented with and/or involving one or more softwareapplications, whether resident on computer devices or platforms,provided for download via a server and/or executed in connection with atleast one network such as via a web application, that include orinvolves features, functionality, computing components and/or stepsconsistent with any set forth herein.

BRIEF DESCRIPTION OF THE DRAWINGS

Various embodiments of the present disclosure can be further explainedwith reference to the attached drawings, wherein like structures arereferred to by like numerals throughout the several views. The drawingsshown are not necessarily to scale, with emphasis instead generallybeing placed upon illustrating the principles of the present disclosure.Therefore, specific structural and functional details disclosed hereinare not to be interpreted as limiting, but merely as a representativebasis for teaching one skilled in the art to variously employ one ormore illustrative embodiments.

FIG. 1 is a block diagram of an exemplary system and/or platforminvolving features of transferring recurring charges, consistent withexemplary aspects of certain embodiments of the present disclosure.

FIG. 2 is a block diagram of an exemplary system and/or platforminvolving features of transferring recurring charges, consistent withexemplary aspects of certain embodiments of the present disclosure.

FIG. 3 is a block diagram of an exemplary computing device that may beassociated with transferring recurring charges, consistent withexemplary aspects of certain embodiments of the present disclosure.

FIG. 4 is diagram illustrating an exemplary sequence of user interfacesand associated computer processing steps, consistent with exemplaryaspects of certain embodiments of the present disclosure.

FIG. 5 is a flowchart illustrating one exemplary process related totransferring recurring charges, consistent with exemplary aspects ofcertain embodiments of the present disclosure.

FIG. 6 is a block diagram depicting an exemplary computer-based systemand/or platform, in accordance with certain embodiments of the presentdisclosure.

FIG. 7 is a block diagram depicting another exemplary computer-basedsystem and/or platform, in accordance with certain embodiments of thepresent disclosure.

FIGS. 8 and 9 are diagrams illustrating two exemplary implementations ofcloud computing architecture/aspects with respect to which the disclosedtechnology may be specifically configured to operate, in accordance withcertain embodiments of the present disclosure.

DETAILED DESCRIPTION

Various detailed embodiments of the present disclosure, taken inconjunction with the accompanying figures, are disclosed herein;however, it is to be understood that the disclosed embodiments aremerely illustrative. In addition, each of the examples given inconnection with the various embodiments of the present disclosure isintended to be illustrative, and not restrictive.

Throughout the specification, the following terms take the meaningsexplicitly associated herein, unless the context clearly dictatesotherwise. The phrases “in one embodiment” and “in some embodiments” asused herein do not necessarily refer to the same embodiment(s), thoughit may. Furthermore, the phrases “in another embodiment” and “in someother embodiments” as used herein do not necessarily refer to adifferent embodiment, although it may. Thus, as described below, variousembodiments may be readily combined, without departing from the scope orspirit of the present disclosure.

Systems and methods associated with providing user interfaces andcomputerized processing features for transferring recurring charges froma first account to a second account are disclosed. In one embodiment, anexemplary method may comprise receiving a request from a user totransfer recurring charges from a first account to a second account,generating a first user interface that enables the user to provideaccount information comprised of a plurality of statements and/oraccount credentials associated with the first account, determining atleast one recurring charge of the first account using the accountinformation, generating a second user interface to display the at leastone recurring charge and prompt the user to submit merchant-relatedcredentials associated with the at least one recurring charge,transferring the merchant-related credentials, and the at least onerecurring charge from the first account to the second account.

FIG. 1 is a block diagram of an exemplary system and/or platform 100involving features of transferring recurring charges as well asgenerating associated user interfaces, in accordance with at least somedisclosed embodiments. System 100 may be configured for executing one ormore software applications, including a financial account applicationinvolving a portal having user interfaces configured for transferringrecurring charges (hereafter “financial account application”) and/or aweb browser application, consistent with disclosed embodiments. Asshown, system 100 may include a computing device 102, such as a clientcomputing device, associated with a user 104. Computing device 102 maybe configured to execute, among other programs, a web browserapplication 108 and a financial account application 111 associated witha financial service provider. System 100 may further include one or morethird-party computers or systems such as those associated with an entity(referred to herein as both a “recurring charge entity” 110 and a“merchant”) involved with providing one or more products, such as goodsor services, to the user 104 and generating recurring charges to a useraccount in exchange for such goods, services, or the like. The recurringcharge entity 110 may operate an account portal 113 for customers thatenables the user 104 to login and manage the user account, includingmaking changes to a payment method (e.g., a user's bank or creditaccount) to which the recurring charges are remitted. System may alsoinclude a first financial services provider (“FSP”) system or server 114having a first (existing) account 117 of the user that is subject to arecurring charge from the recurring charge entity 110, as well as asecond financial services provider (FSP) system or server 112 having asecond (new) account 115 to which the recurring charges are to betransferred. The second FSP system or server 112 may also provide thefinancial account application 111 that is provided to the user andincludes features and functionality for transferring the recurringcharges from the first account 117 to the second account 115. As shown,client computing device 102, recurring charge entity 110, first FSPsystem 114, second FSP system 112 may be communicatively coupled by anetwork 116. Various features, functionality and benefits of financialaccount application 111 may also be achieved via a financial accountapplications or subcomponents 111 within or executed by the clientcomputing device 102. For simplicity of explanation, the behavior of thefinancial account application 111 is discussed generally, below, withoutreferring to or differentiating its performance on the client computingdevice 102 versus the second FSP system 112.

While only the computing device 102, application 108 and 111, entity110, FSP system 112 and 114, account portal 113, and network 116 shownin FIG. 1 are discussed herein, it will be understood that system 100may include additional ones of any of these components. More generally,the components and arrangement of the components included in system 100may vary. Thus, system 100 may include other components that perform orassist in the performance of one or more processes consistent with thedisclosed embodiments. Computing device 102 may be one or more computingdevices configured to perform operations consistent with executing thefinancial account application 111 and/or the web browser application108. One illustrative computing device 102 is further described below inconnection with FIG. 3.

Web browser application 108 may be one or more software applicationsconfigured to perform operations consistent with providing web ornetwork pages to the user, accessing the financial account application111 (such as via a portal), as set forth herein, as well as interactingwith the financial account application 111, and the like. Here, forexample, web browser application 108 may be configured to providevarious information, associated with accessing user interfaces and/orpages related to the user's 104 activity with the second FSP system 112.Such processing may occur by or with a web browser application 108,locally on the client computing device 102, or the web browserapplication 108 may transmit requests to and/or operate with one or moreother software applications and/or computing components to process thedesired information. Web browser application 108 may also be hostedand/or operated, in whole or in part, by a web browser system and/orserver, such as the example system described below in connection withFIG. 2. Web browser application 108 is further described below inconnection with FIG. 3.

In general, first FSP system 114 and second FSP system 112 may each beassociated with a financial service entity that provides, maintains,manages, or otherwise offers financial services. For example, thefinancial service entity may be a bank, credit card issuer, or any othertype of financial service entity that generates, provides, manages,and/or maintains financial service accounts for one or more customers.Financial service accounts may include, for example, credit cardaccounts, loan accounts, checking accounts, savings accounts, reward orloyalty program accounts, and/or any other type of financial serviceaccount known to those skilled in the art. These FSP systems 112 and 114may be one or more computing devices configured to perform operationsconsistent with servicing or maintaining financial service accounts,including a financial service account associated with user 104. FSPsystems 112 and 114 may be further configured to manage existingaccounts, generate new accounts, and process financial transactionsassociated with such financial service accounts. In some embodiments,second FSP system 112 may be further configured to generate a portal andassociated user interfaces for a display device included in, orconnected to, computing device 102, e.g. via financial accountapplication 111, which may be a desktop or mobile banking or other suchapplication, on computing device 102. Alternatively or additionally,second FSP system 112 may be configured to provide such accountmanagement functionality through one or more online portals and/or userinterfaces that are accessible by computing device 102 over network 116.The disclosed embodiments are not limited to any particularconfiguration of second FSP system 112.

Financial account application 111 may be one or more softwareapplications, modules, routines, subroutines and/or extensionsconfigured to perform operations consistent with accessing, using and/ormanaging information related to the user's interactions with the secondFSP system 112, such as a portal that provides user interfaces as wellas other features and functionality associated with the user'smanagement of their accounts with the second FSP system 112.

Recurring charge entity 110 may be an entity associated with one or morecomputing devices that are being operated in connection with providingone or more goods or services to the user. The recurring chargeentities, in turn, issues recurring charges to a first account 117 of auser, which the user may wish to be transferred to a second account 115in accordance with embodiments here. Recurring charge entity 110 mayalso provide an account portal for the user and other customer, by whichsuch individuals may manage their subscriptions or other accounts thatare the genesis of the recurring charges.

Network 116 may be any type of network configured to providecommunication between components of system 100. For example, network 116may be any type of network (including infrastructure) that providescommunications, exchanges information, and/or facilitates the exchangeof information, such as the Internet, a Local Area Network, near fieldcommunication (NFC), optical code scanner, or other suitableconnection(s) that enables the sending and receiving of informationbetween the components of system 100. In other embodiments, one or morecomponents of system 100 may communicate directly through a dedicatedcommunication link(s).

It is to be understood that the configuration and boundaries of thefunctional building blocks of system 100 have been defined herein forthe convenience of the description. Alternative boundaries can bedefined so long as the specified functions and relationships thereof areappropriately performed. Alternatives (including equivalents,extensions, variations, deviations, etc., of those described herein)will be apparent to persons skilled in the relevant art(s) based on theteachings contained herein. Such alternatives fall within the scope andspirit of the disclosed embodiments.

FIG. 2 is a block diagram of an exemplary web browser system 200,consistent with disclosed embodiments. As shown, web browser system 200may include web browser server 202 and web browser application 204. Webbrowser server 202 may include a communication device 206, one or moreprocessor(s) 208, and memory 210 including one or more programs 212 anddata 214. Web browser server 202 may be configured to perform operationsconsistent with providing web browser application 204.

Web browser server 202 may take the form of a server, general purposecomputer, mainframe computer, or any combination of these components.Other implementations consistent with disclosed embodiments are possibleas well. Web browser application 204 may take the form of one or moresoftware applications stored on a computing device, such as web browserapplication 108 stored on computing device 102 described above.

Communication device 206 may be configured to communicate with one ormore computing devices, such as computing device 102. In someembodiments, communication device 206 may be configured to communicatewith the computing device(s) through web browser application 204. Webbrowser server 202 may, for example, be configured to provideinstructions and/or operating information to web browser application 204through communication device 206. Communication device 206 may beconfigured to communicate other information as well.

Communication device 206 may be further configured to communicate withone or more FSP systems, such as first FSP system 114 and second FSPsystem 112 described above, and/or with other entities, such asrecurring charge entity 110 described above. In some embodiments, suchFSP systems 112, 114 may provide a financial service account associatedwith a computing device, and communication device 206 may be configuredto communicate with the FSP system(s) to generate, transmit and/orprocess account-related information or instructions regarding thefinancial service account associated with the computing device.Communication device 206 may be configured to communicate with the FSPsystem(s) in other manners. Communication device 206 may be configuredto communicate with other components as well.

Processor(s) 208 may include one or more known processing devices, suchas a microprocessor from the Core™, Pentium™ or Xeon™ familymanufactured by Intel®, the Turion™ family manufactured by AMD™, the“Ax” (i.e., A6 or A8 processors) or “Sx” (i.e. S1, . . . processors)family manufactured by Apple™, or any of various processors manufacturedby Sun Microsystems, for example. The disclosed embodiments are notlimited to any type of processor(s) otherwise configured to meet thecomputing demands required of different components of web browser system200.

Memory 210 may include one or more storage devices configured to storeinstructions used by processor(s) 208 to perform functions related todisclosed embodiments. For example, memory 210 may be configured withone or more software instructions, such as program(s) 212, that mayperform one or more operations when executed by processor(s) 208. Suchoperations may include web browsing activities as well as creationand/or management of user accounts managed over the world wide web, suchas financial accounts with FSP systems 112,114. The disclosedembodiments are not limited to separate programs or computers configuredto perform dedicated tasks. For example, memory 210 may include a singleprogram 212 that performs the functions of web browser system 200, orprogram(s) 212 may comprise multiple programs. Memory 210 may also storedata 214 that is used by program(s) 212.

In certain embodiments, memory 210 may store one or more sets ofinstructions involved with carrying out the processes described herein,such as those set forth in connection with FIGS. 4 and 5. Otherinstructions are possible as well. In general, instructions may beexecuted by processor(s) 208 to perform one or more processes consistentwith disclosed embodiments. In some embodiments, program(s) 212 mayinclude one or more subcomponents configured to generate and/or processinstructions and information for use by web browser application 204 inperforming creation and/or management activities associated with onlineaccounts.

The components of web browser system 200 may be implemented in hardware,software, or a combination of both hardware and software, as will beapparent to those skilled in the art. For example, although one or morecomponents of web browser system 200 may be implemented as computerprocessing instructions, all or a portion of the functionality of webbrowser system 200 may be implemented instead in dedicated electronicshardware. In some embodiments, web browser system 200 may also becommunicatively connected to one or more database(s) (not shown).Alternatively, such database(s) may be located remotely from web browsersystem 200. Web browser system 200 may be communicatively connected tosuch database(s) through a network, such as network 116 described above.Such database(s) may include one or more memory devices that storeinformation and are accessed and/or managed through web browser system200. By way of example, such database(s) may include Oracle™ databases,Sybase™ databases, or other relational databases or non-relationaldatabases, such as Hadoop sequence files, HBase, or Cassandra. Suchdatabase(s) may include computing components (e.g., database managementsystem, database server, etc.) configured to receive and processrequests for data stored in memory devices of the database(s) and toprovide data to the database(s).

FIG. 3 is a block diagram of an exemplary computing device 300,consistent with disclosed embodiments. As shown, computing device 300may include communication device 302, display device 304, processor(s)306, and memory 308 including program(s) 310 and data 312. Program(s)310 may include, among others, web browser application 314 and financialaccount application 316. In some embodiments, computing device 300 maytake the form of a desktop or mobile computing device, such as a desktopcomputer, laptop computer, smartphone, tablet, or any combination ofthese components. Alternatively, computing device 300 may be configuredas any wearable item, including jewelry, smart glasses, or any otherdevice suitable for carrying or wearing on a user's person. Otherimplementations consistent with disclosed embodiments are possible aswell. Computing device 300 may, for example, be the same as or similarto computing device 102 described above.

In the example embodiment shown, communication device 302 may beconfigured to communicate via one or more networks with the variouscomputer systems and servers disclosed elsewhere herein. In someembodiments, communication device 302 may be further configured tocommunicate with one or more other entities including FSP systems, suchas FSP systems 112, 114 described above, and recurring charge entity 110also described above. Communication device 302 may be configured tocommunicate with other components as well. Communication device 302 maybe configured to provide communication over a network, such as network116 described above. To this end, communication device 302 may include,for example, one or more digital and/or analog devices that allowcomputing device 300 to communicate with and/or detect other components,such as a network controller and/or wireless adaptor for communicatingover the Internet. Other implementations consistent with disclosedembodiments are possible as well.

Display device 304 may be any display device configured to displayinterfaces on computing device 300. The interfaces may include, forexample, web pages provided by computing device 300 through web browserapplication 314. In some embodiments, display device 304 may include ascreen for displaying a graphical and/or text-based user interface,including but not limited to, liquid crystal displays (LCD), lightemitting diode (LED) screens, organic light emitting diode (OLED)screens, and other known display devices. In some embodiments, displaydevice 304 may also include one or more digital and/or analog devicesthat allow a user to interact with computing device 300, such as atouch-sensitive area, keyboard, buttons, or microphones. Other displaydevices are possible as well. The disclosed embodiments are not limitedto any type of display devices otherwise configured to displayinterfaces.

Processor(s) 306 may include one or more known processing devices, suchas a microprocessor from the Core™, Pentium™ or Xeon™ familymanufactured by Intel™, the Turion™ family manufactured by AMD™, the“Ax” or “Sx” family manufactured by Apple™, or any of various processorsmanufactured by Sun Microsystems, for example. Processor(s) 306 may alsoinclude various architectures (e.g., x86 processor, ARM®, etc.). Thedisclosed embodiments are not limited to any type of processor(s)otherwise configured to meet the computing demands required of differentcomponents of computing device 300.

Memory 308 may include one or more storage devices configured to storeinstructions used by processor(s) 306 to perform functions related todisclosed embodiments. For example, memory 308 may be configured withone or more software instructions, such as program(s) 310, that mayperform one or more operations when executed by processor(s) 306. Thedisclosed embodiments are not limited to separate programs or computersconfigured to perform dedicated tasks. For example, memory 308 mayinclude a single program 310 that performs the functions of computingdevice 300, or program(s) 310 may comprise multiple programs. Memory 308may also store data 312 that is used by program(s) 310. In certainembodiments, memory 308 may store sets of instructions for carrying outvarious processes, such as those performed in connection with FIGS. 4and 5. Other instructions are possible as well. In general, instructionsmay be executed by processor(s) 306 to perform one or more processesconsistent with disclosed embodiments.

In some embodiments, program(s) 310 may include a web browserapplication 314. Web browser application 314 may be executable byprocessor(s) 306 to perform operations including, for example, providingweb pages, including login pages requiring user credentials, fordisplay, and/or managing user's online accounts. Such web pages may beprovided, for example, via display device 304. In some embodiments, theweb pages may be associated with systems, such as FSP systems 112 and114, recurring charge entity 110, and the like, described above. Webbrowser application 314 may be executable by processor(s) 306 to performother operations as well. In some embodiments, program(s) 310 mayfurther include a financial account application 316. Financial accountapplication 316 may, for example, be the same as similar to financialaccount application 111 of client computing device 102 described above.Financial account application 316 may be executable by processor(s) 306to perform various operations including, for example, creating and/ormanaging financial accounts of the user by computing device 300 via webbrowser application 314. Other instructions are possible as well. Ingeneral, instructions may be executed by processor(s) 306 to perform oneor more processes consistent with disclosed embodiments.

The components of computing device 300 may be implemented in hardware,software, or a combination of both hardware and software, as will beapparent to those skilled in the art. For example, although one or morecomponents of computing device 300 may be implemented as computerprocessing instructions, all or a portion of the functionality ofcomputing device 300 may be implemented instead in dedicated electronicshardware.

FIG. 4 is diagram illustrating an exemplary sequence of user interfacesand associated computer processing steps, consistent with exemplaryaspects of certain embodiments of the present disclosure. FIG. 4 depictsan illustrative sequence of three screens and four steps associated withan exemplary process of transferring recurring charges from a firstaccount to a second account. The exemplary sequence of FIG. 4 beginswith a first step (Step 1) that includes displaying a first userinterface 410, e.g. Screen 1, upon receipt of the user's authorizationto begin transferring one or more recurring charges from a first accountto a second account. In some embodiments, the user may be a customer ofanother bank or financial institution, such as first FSP system 114, andthe user interfaces may be provided via a second bank or financialinstitution, such as second FSP system 112, which provides the userinterfaces and functionality as part of procuring new customers fromother financial institutions. Here, for example, the second FSP system112 may incentivize the user to migrate an account, such as a creditcard account with a balance and recurring charges, by generating a newaccount having more favorable terms than the user's existing account.

Turning back to FIG. 4, the first user interface 410 may be generatedwith one or both of a first input portal 422 and/or a second inputportal 432, by which the user may provide the information that is neededfor the second FSP system to identify any charges associated withaccounts being transferred that are recurring charges. In someembodiments, a first input portal 422 may be provided to allow the userto upload bank or account statements to be analyzed on the back-end(e.g., by the second FSP system 112) to identify recurring charges.Here, for example, the first input portal 422 may comprise a firstinteractive field 424 that enables the user to drag and drop filescorresponding to statements that the user would like to be analyzed forpossible recurring charges. Other UI tools may be provided to identifyor attach files or statements associated with the user's account, suchas a file search or navigation tool that allows the user to browsethrough folders and select files. Further, the first input portal 422may also include one or more buttons or UI elements 426 which may beselected, after the file(s) are identified, to process, upload and/orsubmit the files (i.e., the user's account statements) identified.

In some embodiments, a second input portal 430 may also, oralternatively, be provided to the user to help identify potentialrecurring charges for transfer from the first account to the secondaccount. Here, for example, a second input portal 430 may be generatedto request and obtain account credentials that enable the second FSPsystem 112 to access the accounts that the user identified and identifyany recurring charges being debited to such accounts. As shown in theexample user interface 410 of FIG. 4, the account credentials receivedby the second input portal 432 may include a first field 434 to receivethe user's username for the account subject to transfer as well as asecond field 436 to receive the user's password for that account. Thesecond input portal 432 may also include a UI element 438 that instructsthe second FSP system 112 to proceed accessing the user account. Othervariations of the functionality illustrated may also be utilized toprovide the second FSP system with sufficient access to the user'saccount(s) to identifying recurring charges.

Once the information needed to identify recurring charges has beenobtain, via the first user interface 410 for example, the exemplarysequence of FIG. 4 may proceed to the second step, at 440. In the secondstep 440, the second FSP system 112 receives the account informationobtain via the first user interface 410 and performs automatedcomputerized processing to determine and identify the recurring chargesbeing debited to the account(s) that the user has identified fortransfer as well as the merchants (i.e., recurring charge entities 110)associated with each recurring charge. Such automated processing isperformed by computing components of the second FSP system 112, such asby backend components of the second FSP system 112. In some embodiments,the automated processing that the second FSP system 112 performs toidentify the recurring charges may comprise, for example, machinelearning techniques involving Naive Bayes classification techniquesand/or algorithms for determination of recurrence relationships.Further, in some embodiments, the machine learning model utilized bysecond FSP system 112 may be trained using supervised learning on sampledata, e.g. available to one or more financial services entities that areassociated with the second FSP system 112, to increase and maintainaccuracy.

Once the recurring charges and associated merchants have been identifiedin the second step 440, the exemplary sequence may proceed to the thirdstep, at 450. In the third step, the second FSP system 112 may generatea second user interface 450 that is configured to display the recurringcharges, via a first display field 460, and prompt the user, at 470, tosubmit merchant-related credentials of merchants associated with therecurring charges displayed in the first display field 460. The seconduser interface 450 may comprise a first display field 460 that includesa listing 462 of the recurring charges and/or associated merchantsidentified in the second step 440. The dates that the recurring chargesoccurred may also be included in the listing 462. The recurring chargesprovided in the listing 462 may also include embedded links that enablethe user to click a link to immediately navigate to a login page of themerchant associated with that recurring charge, e.g., to facilitateupdating the account information to which the respective recurringcharges are debited. In another embodiment, the user may be redirectedto a separate online tool or portal having user interfaces and/orinteractive UI elements that enable the user to update bank or paymentinformation of merchant accounts associated with the recurring chargesthat are being transferred to the second FSP system 112.

The second user interface 450 may further comprise a second displayfield 470 that includes one or more entry fields 472, 480, such as oneentry field for each of the merchants identified as having recurringcharges to the user account being transferred. The entry fields 472, 480may be configured to prompt the user to submit merchant-relatedcredentials to access the accounts of the merchants identified as havingrecurring charges to the user. In some embodiments, the entry fields472, 480 may comprise a username field 474, 482 and a password field476, 484, by which the user is prompted to enter merchant-related logincredentials. Here, for example, these merchant-related login credentialsmay be the credentials needed to login to and manage the user accountsthat the user has with the merchants behind the recurring chargesidentified. With these merchant-related credentials received, the secondFSP system 112 may perform automated processing to navigate to themerchant web sites, login to the user's account, and update the paymentinformation for the recurring charge to the second account 115 at thesecond FSP system 112. In other embodiments, the second FSP system 112may directly access one or more API (application programming interfaces)associated with the merchant to update the recurring charge to the newaccount.

FIG. 5 is a flowchart illustrating one exemplary method 500 related toprovision of a portal for users to transfer recurring charges betweencustomer accounts, consistent with exemplary aspects of at least someembodiments of the present disclosure. As shown in the exemplaryflowchart of FIG. 5, one method of transferring recurring charges 500may comprise: receiving a request from a user to transfer recurringcharges from a first account of a first financial institution to asecond account of a second financial institution, at 502; generating afirst user interface that enables the user to provide accountinformation associated with first account, wherein the accountinformation comprises (i) a plurality of statements associated with thefirst account, (ii) account credentials associated with the firstaccount, or both, at 504; determining, using the account information, atleast one recurring charge of the first account, at 506; generating asecond user interface that is configured to: (i) display to the user theat least one recurring charge, and (ii) prompt the user to submitmerchant-related credentials associated with the at least one recurringcharge, at 508; and transferring, using the merchant-relatedcredentials, the at least one recurring charge from the first account tothe second account. The merchant-related credentials may be, forexample, a username and a password associated with an online account ofa merchant or recurring charge entity 110 that provides goods orservices to a customer in connection with issuing recurring charges toan associated customer. In some embodiments, the account credentialsassociated with the first account, in step 510, may comprise a usernameand password for the first account 117 of the first FSP system 114.

As explained above in connection with FIG. 4, in some embodiments, thestep of determining the at least one recurring charge 506 may includedetermining such recurring charge(s) based on the user's submissionplurality of statements, such as statements provided via firstinteractive field 422 in FIG. 4. Further, the step of determining the atleast one recurring charge 506 may also include accessing information,e.g. based on information entered via a second interactive field 432 inFIG. 4, about a plurality of charges of the first account using theaccount credentials 434, 436, and determining the at least one recurringcharge based on the information about the plurality of charges.

Once recurring charges have been identified, various features may beutilized to transfer such recurring charges or debits from the firstaccount to the second account. According to certain embodiments, forexample, transferring the at least one recurring charge from the firstaccount to the second account 510 may comprise instructing, using themerchant-related credentials (e.g., 474/476, 482/484, or the like), amerchant associated with the at least one recurring charge to charge allfuture recurring charges to the second account. As explained above, suchmerchant-related credentials associated with such recurring charge maycomprise a username 474/482 and a password 476/484 for a merchantaccount associated with a recurring charge to be transferred. Further,in some implementations, the step of transferring the at least onerecurring charge from the first account to the second account 510 maycomprise directly accessing, e.g. by a computer associated with thesecond financial institution using the merchant-related credentials(e.g., 474/476, 482/484, etc.), an account of a merchant associated witha recurring charge identified for transfer, and instructing the merchantaccount to debit all of the future recurring charge to the secondaccount.

The financial account application 111 may provide other features andfunctionality in connection with transferring the recurring charge tothe second account. According to certain embodiments, for example, thefinancial account application 111 may approve the user to transfer abalance from the first account 117 to the second account 115, whileadditionally providing the user interfaces and functionality herein toalso transfer the recurring charges associated with the first account tothe second account.

In some embodiments, the financial account application 111 may alsogenerate and display various other user interfaces and/or graphicalindicia that provide additional features and benefits to the user. Forexample, the financial account application 111 may provide a listing ofrecurring charges transferred from the first account to the secondaccount, e.g., for display on a display device of the user to facilitatethe user's comprehension and management of the recurring charges beingtransferred. Similarly, the financial account application 111 maydisplay text or graphical indicia, such as another user interface or UIelement, that communicates a transfer status of a recurring charge or alisting of recurring charges to the user, e.g., to indicate thattransfers are in process, completed, or the like.

FIG. 6 depicts a block diagram of an exemplary computer-basedsystem/platform in accordance with one or more embodiments of thepresent disclosure. However, not all of these components may be requiredto practice one or more embodiments, and variations in the arrangementand type of the components may be made without departing from the spiritor scope of various embodiments of the present disclosure. In someembodiments, the exemplary inventive computing devices and/or theexemplary inventive computing components of the exemplary computer-basedsystem/platform may be configured to manage a large number of users(e.g., clients, and their users) and/or concurrent interactions, asdetailed herein. In some embodiments, the exemplary computer-basedsystem/platform may be based on a scalable computer and/or networkarchitecture that incorporates varies strategies for assessing the data,caching, searching, and/or database connection pooling. An example ofthe scalable architecture is an architecture that is capable ofoperating multiple servers.

In some embodiments, referring to FIG. 6, members 602-604 (e.g.,clients) of the exemplary computer-based system/platform may includevirtually any computing device capable of receiving and sending amessage over a network (e.g., organization intranet, cloud network,etc.), such as network 605, to and from another computing device, suchas servers 606 and 607, each other, and the like. In some embodiments,the member devices 602-604 may be personal computers, multiprocessorsystems, microprocessor-based or programmable consumer electronics,network PCs, and the like. In some embodiments, one or more memberdevices within member devices 602-604 may include computing devices thattypically connect using a wireless communications medium such as cellphones, smart phones, pagers, walkie talkies, radio frequency (RF)devices, infrared (IR) devices, CBs, integrated devices combining one ormore of the preceding devices, or virtually any mobile computing device,and the like. In some embodiments, one or more member devices withinmember devices 602-604 may be devices that are capable of connectingusing a wired or wireless communication medium such as a PDA, POCKET PC,wearable computer, a laptop, tablet, desktop computer, a netbook, avideo game device, a pager, a smart phone, an ultra-mobile personalcomputer (UMPC), and/or any other device that is equipped to communicateover a wired and/or wireless communication medium (e.g., NFC, RFID,NBIOT, 3G, 4G, 5G, GSM, GPRS, WiFi, WiMax, CDMA, satellite, ZigBee,etc.). In some embodiments, one or more member devices within memberdevices 602-604 may include may run one or more applications, such asInternet browsers, mobile applications, voice calls, video games,videoconferencing, and email, among others. In some embodiments, one ormore member devices within member devices 602-604 may be configured toreceive and to send web pages, and the like. In some embodiments, anexemplary specifically programmed network/web browser application of thepresent disclosure may be configured to receive and display graphics,text, multimedia, and the like, employing virtually any web basedlanguage, including, but not limited to Standard Generalized MarkupLanguage (SMGL), such as HyperText Markup Language (HTML), a wirelessapplication protocol (WAP), a Handheld Device Markup Language (HDML),such as Wireless Markup Language (WML), WMLScript, XML, JavaScript, andthe like. In some embodiments, a member device within member devices602-604 may be specifically programmed by either Java, .Net, QT, C, C++and/or other suitable programming language. In some embodiments, one ormore member devices within member devices 602-604 may be specificallyprogrammed include or execute an application to perform a variety ofpossible tasks, such as, without limitation, messaging functionality,browsing, searching, playing, streaming or displaying various forms ofcontent, including locally stored or uploaded messages, images and/orvideo, and/or games.

In some embodiments, the exemplary network 605 may provide networkaccess, data transport and/or other services to any computing devicecoupled to it. In some embodiments, the exemplary network 605 mayinclude and implement at least one specialized network architecture thatmay be based at least in part on one or more standards set by, forexample, without limitation, GlobalSystem for Mobile communication (GSM)Association, the Internet Engineering Task Force (IETF), and theWorldwide Interoperability for Microwave Access (WiMAX) forum. In someembodiments, the exemplary network 605 may implement one or more of aGSM architecture, a General Packet Radio Service (GPRS) architecture, aUniversal Mobile Telecommunications System (UMTS) architecture, and anevolution of UMTS referred to as Long Term Evolution (LTE). In someembodiments, the exemplary network 605 may include and implement, as analternative or in conjunction with one or more of the above, a WiMAXarchitecture defined by the WiMAX forum. In some embodiments and,optionally, in combination of any embodiment described above or below,the exemplary network 605 may also include, for instance, at least oneof a local area network (LAN), a wide area network (WAN), the Internet,a virtual LAN (VLAN), an enterprise LAN, a layer 3 virtual privatenetwork (VPN), an enterprise IP network, or any combination thereof. Insome embodiments and, optionally, in combination of any embodimentdescribed above or below, at least one computer network communicationover the exemplary network 605 may be transmitted based at least in parton one of more communication modes such as but not limited to: NFC,RFID, Narrow Band Internet of Things (NBIOT), ZigBee, 3G, 4G, 5G, GSM,GPRS, WiFi, WiMax, CDMA, satellite and any combination thereof. In someembodiments, the exemplary network 605 may also include mass storage,such as network attached storage (NAS), a storage area network (SAN), acontent delivery network (CDN) or other forms of computer- ormachine-readable media.

In some embodiments, the exemplary server 606 or the exemplary server607 may be a web server (or a series of servers) running a networkoperating system, examples of which may include but are not limited toMicrosoft Windows Server, Novell NetWare, or Linux. In some embodiments,the exemplary server 606 or the exemplary server 607 may be used forand/or provide cloud and/or network computing. Although not shown inFIG. 1, in some embodiments, the exemplary server 606 or the exemplaryserver 607 may have connections to external systems like email, SMSmessaging, text messaging, ad content providers, etc. Any of thefeatures of the exemplary server 606 may be also implemented in theexemplary server 607 and vice versa.

In some embodiments, one or more of the exemplary servers 606 and 607may be specifically programmed to perform, in non-limiting example, asauthentication servers, search servers, email servers, social networkingservices servers, SMS servers, IM servers, MMS servers, exchangeservers, photo-sharing services servers, advertisement providingservers, financial/banking-related services servers, travel servicesservers, or any similarly suitable service-base servers for users of themember computing devices 601-604.

In some embodiments and, optionally, in combination of any embodimentdescribed above or below, for example, one or more exemplary computingmember devices 602-604, the exemplary server 606, and/or the exemplaryserver 607 may include a specifically programmed software module thatmay be configured to send, process, and receive information using ascripting language, a remote procedure call, an email, a tweet, ShortMessage Service (SMS), Multimedia Message Service (MMS), instantmessaging (IM), internet relay chat (IRC), mIRC, Jabber, an applicationprogramming interface, Simple Object Access Protocol (SOAP) methods,Common Object Request Broker Architecture (CORBA), HTTP (HypertextTransfer Protocol), REST (Representational State Transfer), or anycombination thereof.

FIG. 7 depicts a block diagram of another exemplary computer-basedsystem/platform 700 in accordance with one or more embodiments of thepresent disclosure. However, not all of these components may be requiredto practice one or more embodiments, and variations in the arrangementand type of the components may be made without departing from the spiritor scope of various embodiments of the present disclosure. In someembodiments, the member computing devices 702 a, 702 b thru 702 n showneach at least includes a computer-readable medium, such as arandom-access memory (RAM) 708 coupled to a processor 710 or FLASHmemory. In some embodiments, the processor 710 may executecomputer-executable program instructions stored in memory 708. In someembodiments, the processor 710 may include a microprocessor, an ASIC,and/or a state machine. In some embodiments, the processor 710 mayinclude, or may be in communication with, media, for examplecomputer-readable media, which stores instructions that, when executedby the processor 710, may cause the processor 710 to perform one or moresteps described herein. In some embodiments, examples ofcomputer-readable media may include, but are not limited to, anelectronic, optical, magnetic, or other storage or transmission devicecapable of providing a processor, such as the processor 710 of client702 a, with computer-readable instructions. In some embodiments, otherexamples of suitable media may include, but are not limited to, a floppydisk, CD-ROM, DVD, magnetic disk, memory chip, ROM, RAM, an ASIC, aconfigured processor, all optical media, all magnetic tape or othermagnetic media, or any other medium from which a computer processor canread instructions. Also, various other forms of computer-readable mediamay transmit or carry instructions to a computer, including a router,private or public network, or other transmission device or channel, bothwired and wireless. In some embodiments, the instructions may comprisecode from any computer-programming language, including, for example, C,C++, Visual Basic, Java, Python, Perl, JavaScript, and etc.

In some embodiments, member computing devices 702 a thru 702 n may alsocomprise a number of external or internal devices such as a mouse, aCD-ROM, DVD, a physical or virtual keyboard, a display, a speaker, orother input or output devices. In some embodiments, examples of membercomputing devices 702 a thru 702 n (e.g., clients) may be any type ofprocessor-based platforms that are connected to a network 605 such as,without limitation, personal computers, digital assistants, personaldigital assistants, smart phones, pagers, digital tablets, laptopcomputers, Internet appliances, and other processor-based devices. Insome embodiments, member computing devices 702 a thru 702 n may bespecifically programmed with one or more application programs inaccordance with one or more principles/methodologies detailed herein. Insome embodiments, member computing devices 702 a thru 702 n may operateon any operating system capable of supporting a browser orbrowser-enabled application, such as Microsoft™ Windows™, and/or Linux.In some embodiments, member computing devices 702 a thru 702 n shown mayinclude, for example, personal computers executing a browser applicationprogram such as Microsoft Corporation's Internet Explorer™, AppleComputer, Inc.'s Safari™, Mozilla Firefox, and/or Opera. In someembodiments, through the member computing client devices 702 a thru 702n, users 712 a thru 712 n, may communicate over the exemplary network605 with each other and/or with other systems and/or devices coupled tothe network 605. As shown in FIG. 7, exemplary server devices 704 and713 may be also coupled to the network 605. In some embodiments, one ormore member computing devices 702 a thru 702 n may be mobile clients.

In some embodiments, at least one database of exemplary databases 707and 715 may be any type of database, including a database managed by adatabase management system (DBMS). In some embodiments, an exemplaryDBMS-managed database may be specifically programmed as an engine thatcontrols organization, storage, management, and/or retrieval of data inthe respective database. In some embodiments, the exemplary DBMS-manageddatabase may be specifically programmed to provide the ability to query,backup and replicate, enforce rules, provide security, compute, performchange and access logging, and/or automate optimization. In someembodiments, the exemplary DBMS-managed database may be chosen fromOracle database, IBM DB2, Adaptive Server Enterprise, FileMaker,Microsoft Access, Microsoft SQL Server, MySQL, PostgreSQL, and a NoSQLimplementation. In some embodiments, the exemplary DBMS-managed databasemay be specifically programmed to define each respective schema of eachdatabase in the exemplary DBMS, according to a particular database modelof the present disclosure which may include a hierarchical model,network model, relational model, object model, or some other suitableorganization that may result in one or more applicable data structuresthat may include fields, records, files, and/or objects. In someembodiments, the exemplary DBMS-managed database may be specificallyprogrammed to include metadata about the data that is stored.

As also shown in FIGS. 7 and 8, some embodiments of the disclosedtechnology may also include and/or involve one or more cloud components725, which are shown grouped together in the drawing for sake ofillustration, though may be distributed in various ways as known in theart. Cloud components 725 may include one or more cloud services such assoftware applications (e.g., queue, etc.), one or more cloud platforms(e.g., a Web front-end, etc.), cloud infrastructure (e.g., virtualmachines, etc.), and/or cloud storage (e.g., cloud databases, etc.).

According to some embodiments shown by way of one example in FIG. 9, theexemplary inventive computer-based systems/platforms, the exemplaryinventive computer-based devices, components and media, and/or theexemplary inventive computer-implemented methods of the presentdisclosure may be specifically configured to operate in or with cloudcomputing/architecture such as, but not limiting to: infrastructure aservice (IaaS) 910, platform as a service (PaaS) 908, and/or software asa service (SaaS) 906. FIGS. 8 and 9 illustrate schematics of exemplaryimplementations of the cloud computing/architecture(s) in which theexemplary inventive computer-based systems/platforms, the exemplaryinventive computer-implemented methods, and/or the exemplary inventivecomputer-based devices, components and/or media of the presentdisclosure may be specifically configured to operate. In someembodiments, such cloud architecture 906, 908, 910 may be utilized inconnection with the web browser and network aspects, shown at 904, toachieve the innovations herein.

As used in the description and in any claims, the term “based on” is notexclusive and allows for being based on additional factors notdescribed, unless the context clearly dictates otherwise. In addition,throughout the specification, the meaning of “a,” “an,” and “the”include plural references. The meaning of “in” includes “in” and “on.”

It is understood that at least one aspect/functionality of variousembodiments described herein can be performed in real-time and/ordynamically. As used herein, the term “real-time” is directed to anevent/action that can occur instantaneously or almost instantaneously intime when another event/action has occurred. For example, the “real-timeprocessing,” “real-time computation,” and “real-time execution” allpertain to the performance of a computation during the actual time thatthe related physical process (e.g., a user interacting with anapplication on a mobile device) occurs, in order that results of thecomputation can be used in guiding the physical process.

As used herein, the term “dynamically” and term “automatically,” andtheir logical and/or linguistic relatives and/or derivatives, mean thatcertain events and/or actions can be triggered and/or occur without anyhuman intervention. In some embodiments, events and/or actions inaccordance with the present disclosure can be in real-time and/or basedon a predetermined periodicity of at least one of: nanosecond, severalnanoseconds, millisecond, several milliseconds, second, several seconds,minute, several minutes, hourly, several hours, daily, several days,weekly, monthly, etc.

As used herein, the term “runtime” corresponds to any behavior that isdynamically determined during an execution of a software application orat least a portion of software application.

In some embodiments, exemplary inventive, specially programmed computingsystems/platforms with associated devices are configured to operate inthe distributed network environment, communicating with one another overone or more suitable data communication networks (e.g., the Internet,satellite, etc.) and utilizing one or more suitable data communicationprotocols/modes such as, without limitation, IPX/SPX, X.25, AX.25,AppleTalk™, TCP/IP (e.g., HTTP), Bluetooth™, near-field wirelesscommunication (NFC), RFID, Narrow Band Internet of Things (NBIOT), 3G,4G, 5G, GSM, GPRS, WiFi, WiMax, CDMA, satellite, ZigBee, and othersuitable communication modes. Various embodiments herein may includeinteractive posters that involve wireless, e.g., Bluetooth™ and/or NFC,communication aspects, as set forth in more detail further below. Insome embodiments, the NFC can represent a short-range wirelesscommunications technology in which NFC-enabled devices are “swiped,”“bumped,” “tap” or otherwise moved in close proximity to communicate. Insome embodiments, the NFC could include a set of short-range wirelesstechnologies, typically requiring a distance of 10 cm or less. In someembodiments, the NFC may operate at 13.56 MHz on ISO/IEC 18000-3 airinterface and at rates ranging from 106 kbit/s to 424 kbit/s. In someembodiments, the NFC can involve an initiator and a target; theinitiator actively generates an RF field that can power a passivetarget. In some embodiments, this can enable NFC targets to take verysimple form factors such as tags, stickers, key fobs, or cards that donot require batteries. In some embodiments, the NFC's peer-to-peercommunication can be conducted when a plurality of NFC-enable devices(e.g., smartphones) are within close proximity of each other.

The material disclosed herein may be implemented in software or firmwareor a combination of them or as instructions stored on a machine-readablemedium, which may be read and executed by one or more processors. Amachine-readable medium may include any medium and/or mechanism forstoring or transmitting information in a form readable by a machine(e.g., a computing device). For example, a machine-readable medium mayinclude read only memory (ROM); random access memory (RAM); magneticdisk storage media; optical storage media; flash memory devices;electrical, optical, acoustical or other forms of propagated signals(e.g., carrier waves, infrared signals, digital signals, etc.), andothers.

As used herein, the terms “computer engine” and “engine” identify atleast one software component and/or a combination of at least onesoftware component and at least one hardware component which aredesigned/programmed/configured to manage/control other software and/orhardware components (such as the libraries, software development kits(SDKs), objects, etc.).

Examples of hardware elements may include processors, microprocessors,circuits, circuit elements (e.g., transistors, resistors, capacitors,inductors, and so forth), integrated circuits, application specificintegrated circuits (ASIC), programmable logic devices (PLD), digitalsignal processors (DSP), field programmable gate array (FPGA), logicgates, registers, semiconductor device, chips, microchips, chip sets,and so forth. In some embodiments, the one or more processors may beimplemented as a Complex Instruction Set Computer (CISC) or ReducedInstruction Set Computer (RISC) processors; x86 instruction setcompatible processors, multi-core, or any other microprocessor orcentral processing unit (CPU). In various implementations, the one ormore processors may be dual-core processor(s), dual-core mobileprocessor(s), and so forth.

Examples of software may include software components, programs,applications, computer programs, application programs, system programs,machine programs, operating system software, middleware, firmware,software modules, routines, subroutines, functions, methods, procedures,software interfaces, application program interfaces (API), instructionsets, computing code, computer code, code segments, computer codesegments, words, values, symbols, or any combination thereof.Determining whether an embodiment is implemented using hardware elementsand/or software elements may vary in accordance with any number offactors, such as desired computational rate, power levels, heattolerances, processing cycle budget, input data rates, output datarates, memory resources, data bus speeds and other design or performanceconstraints.

One or more aspects of at least one embodiment may be implemented byrepresentative instructions stored on a machine-readable medium whichrepresents various logic within the processor, which when read by amachine causes the machine to fabricate logic to perform the techniquesdescribed herein. Such representations, known as “IP cores” may bestored on a tangible, machine readable medium and supplied to variouscustomers or manufacturing facilities to load into the fabricationmachines that make the logic or processor. Of note, various embodimentsdescribed herein may, of course, be implemented using any appropriatehardware and/or computing software languages (e.g., C++, Objective-C,Swift, Java, JavaScript, Python, Perl, QT, etc.).

In some embodiments, one or more of exemplary inventive computer-basedsystems/platforms, exemplary inventive computer-based devices, and/orexemplary inventive computer-based components of the present disclosuremay include or be incorporated, partially or entirely into at least onepersonal computer (PC), laptop computer, ultra-laptop computer, tablet,touch pad, portable computer, handheld computer, palmtop computer,personal digital assistant (PDA), cellular telephone, combinationcellular telephone/PDA, television, smart device (e.g., smart phone,smart tablet, smart television, etc.), mobile internet device (MID),messaging device, data communication device, and so forth.

As used herein, term “server” should be understood to refer to a servicepoint which provides processing, database, and communication facilities.By way of example, and not limitation, the term “server” can refer to asingle, physical processor with associated communications and datastorage and database facilities, or it can refer to a networked orclustered complex of processors and associated network and storagedevices, as well as operating software and one or more database systemsand application software that support the services provided by theserver. Cloud components (e.g., FIG. 8-9) and cloud servers areexamples.

In some embodiments, as detailed herein, one or more of exemplaryinventive computer-based systems/platforms, exemplary inventivecomputer-based devices, and/or exemplary inventive computer-basedcomponents of the present disclosure may obtain, manipulate, transfer,store, transform, generate, and/or output any digital object and/or dataunit (e.g., from inside and/or outside of a particular application) thatcan be in any suitable form such as, without limitation, a file, acontact, a task, an email, a tweet, a map, an entire application (e.g.,a calculator), etc. In some embodiments, as detailed herein, one or moreof exemplary inventive computer-based systems/platforms, exemplaryinventive computer-based devices, and/or exemplary inventivecomputer-based components of the present disclosure may be implementedacross one or more of various computer platforms such as, but notlimited to: (1) AmigaOS, AmigaOS 4; (2) FreeBSD, NetBSD, OpenBSD; (3)Linux; (4) Microsoft Windows; (5) OpenVMS; (6) OS X (Mac OS); (7) OS/2;(8) Solaris; (9) Tru64 UNIX; (10) VM; (11) Android; (12) Bada; (13)BlackBerry OS; (14) Firefox OS; (15) Ios; (16) Embedded Linux; (17) PalmOS; (18) Symbian; (19) Tizen; (20) WebOS; (21) Windows Mobile; (22)Windows Phone; (23) Adobe AIR; (24) Adobe Flash; (25) Adobe Shockwave;(26) Binary Runtime Environment for Wireless (BREW); (27) Cocoa (API);(28) Cocoa Touch; (29) Java Platforms; (30) JavaFX; (31) JavaFX Mobile;(32) Microsoft XNA; (33) Mono; (34) Mozilla Prism, XUL and XULRunner;(35) .NET Framework; (36) Silverlight; (37) Open Web Platform; (38)Oracle Database; (39) Qt; (40) SAP NetWeaver; (41) Smartface; (42) Vexi;and/OR (43) Windows Runtime.

In some embodiments, exemplary inventive computer-basedsystems/platforms, exemplary inventive computer-based devices, and/orexemplary inventive computer-based components of the present disclosuremay be configured to utilize hardwired circuitry that may be used inplace of or in combination with software instructions to implementfeatures consistent with principles of the disclosure. Thus,implementations consistent with principles of the disclosure are notlimited to any specific combination of hardware circuitry and software.For example, various embodiments may be embodied in many different waysas a software component such as, without limitation, a stand-alonesoftware package, a combination of software packages, or it may be asoftware package incorporated as a “tool” in a larger software product.

For example, exemplary software specifically programmed in accordancewith one or more principles of the present disclosure may bedownloadable from a network, for example, a website, as a stand-aloneproduct or as an add-in package for installation in an existing softwareapplication. For example, exemplary software specifically programmed inaccordance with one or more principles of the present disclosure mayalso be available as a client-server software application, or as aweb-enabled software application. For example, exemplary softwarespecifically programmed in accordance with one or more principles of thepresent disclosure may also be embodied as a software package installedon a hardware device.

In some embodiments, exemplary inventive computer-basedsystems/platforms, exemplary inventive computer-based devices, and/orexemplary inventive computer-based components of the present disclosuremay be configured to output to distinct, specifically programmedgraphical user interface implementations of the present disclosure(e.g., a desktop, a web app., etc.). In various implementations of thepresent disclosure, a final output may be displayed on a displayingscreen which may be, without limitation, a screen of a computer, ascreen of a mobile device, a virtually generated display, or the like.In various implementations, the display may be a holographic display. Invarious implementations, the display may be a transparent surface thatmay receive a visual projection. Such projections may convey variousforms of information, images, and/or objects. For example, suchprojections may be a visual overlay for a mobile augmented reality (MAR)application.

In some embodiments, exemplary inventive computer-basedsystems/platforms, exemplary inventive computer-based devices, and/orexemplary inventive computer-based components of the present disclosuremay be configured to be utilized in various applications which mayinclude, but not limited to, gaming, mobile-device games, video chats,video conferences, live video streaming, video streaming and/oraugmented reality applications, mobile-device messenger applications,and others similarly suitable computer-device applications.

As used herein, the term “mobile electronic device,” or the like, mayrefer to any portable electronic device that may or may not be enabledwith location tracking functionality (e.g., MAC address, InternetProtocol (IP) address, or the like). For example, a mobile electronicdevice can include, but is not limited to, a mobile phone, PersonalDigital Assistant (PDA), Blackberry™, Pager, Smartphone, smart watch,wearable or any other reasonable mobile electronic device.

As used herein, terms “proximity detection,” “locating,” “locationdata,” “location information,” and “location tracking” refer to any formof location tracking technology or locating method that can be used toprovide a location of, for example, a particular computingdevice/system/platform of the present disclosure and/or any associatedcomputing devices, based at least in part on one or more of thefollowing techniques/devices, without limitation: accelerometer(s),gyroscope(s), Global Positioning Systems (GPS); GPS accessed usingBluetooth™; GPS accessed using any reasonable form of wireless and/ornon-wireless communication; WiFi™ server location data; Bluetooth™ basedlocation data; triangulation such as, but not limited to, network basedtriangulation, WiFi™ server information based triangulation, Bluetooth™server information based triangulation; Cell Identification basedtriangulation, Enhanced Cell Identification based triangulation,Uplink-Time difference of arrival (U-TDOA) based triangulation, Time ofarrival (TOA) based triangulation, Angle of arrival (AOA) basedtriangulation; techniques and systems using a geographic coordinatesystem such as, but not limited to, longitudinal and latitudinal based,geodesic height based, Cartesian coordinates based; Radio FrequencyIdentification such as, but not limited to, Long range RFID, Short rangeRFID; using any form of RFID tag such as, but not limited to active RFIDtags, passive RFID tags, battery assisted passive RFID tags; or anyother reasonable way to determine location. For ease, at times the abovevariations are not listed or are only partially listed; this is in noway meant to be a limitation.

As used herein, terms “cloud,” “Internet cloud,” “cloud computing,”“cloud architecture,” and similar terms correspond to at least one ofthe following: (1) a large number of computers connected through areal-time communication network (e.g., Internet); (2) providing theability to run a program or application on many connected computers(e.g., physical machines, virtual machines (VMs)) at the same time; (3)network-based services, which appear to be provided by real serverhardware, and are in fact served up by virtual hardware (e.g., virtualservers), simulated by software running on one or more real machines(e.g., allowing to be moved around and scaled up (or down) on the flywithout affecting the end user).

The aforementioned examples are, of course, illustrative and notrestrictive.

As used herein, the term “user” shall have a meaning of at least oneuser. In some embodiments, the terms “user”, “subscriber”, “consumer”,or “customer” should be understood to refer to a user of an applicationor applications as described herein and/or a consumer of data suppliedby a data provider. By way of example, and not limitation, the terms“user” or “subscriber” can refer to a person who receives data providedby the data or service provider over the Internet in a browser session,or can refer to an automated software application which receives thedata and stores or processes the data.

At least some aspects of the present disclosure will now be describedwith reference to the following numbered clauses.

Clause 1. A computer-implemented method comprising:

receiving, by at least one computing processor, a request from a user totransfer recurring charges from a first account of a first financialinstitution to a second account of a second financial institution;

generating, by the at least one computing processor, a first userinterface that enables the user to provide account informationassociated with first account, wherein the account information comprises(i) a plurality of statements associated with the first account, (ii)account credentials associated with the first account, or both (i) and(ii);

determining, by the at least one computing processor and using theaccount information, at least one recurring charge of the first account;

generating, by the at least one computing processor, a second userinterface that is configured to:

(i) display to the user the at least one recurring charge, and

(ii) prompt the user to submit merchant-related credentials associatedwith the at least one recurring charge; and

transferring, by the at least one computing processor and using themerchant-related credentials, the at least one recurring charge from thefirst account to the second account.

Clause 2. The method of clause 1 or any embodiment of the presentdisclosure, wherein determining the at least one recurring charge isbased on the plurality of statements.Clause 3. The method of clause 1 or any embodiment of the presentdisclosure, wherein determining the at least one recurring chargeincludes accessing, by the at least one computing processor, informationabout a plurality of charges of the first account using the accountcredentials, and determining the at least one recurring charge based onthe information about the plurality of charges.Clause 4. The method of clause 1 or any embodiment of the presentdisclosure, wherein transferring the at least one recurring charge fromthe first account to the second account comprises:

instructing, by the at least one computing processor and using themerchant-related credentials, a merchant associated with the at leastone recurring charge to charge in the future the at least one recurringcharge to the second account.

Clause 5. The method of clause 1 or any embodiment of the presentdisclosure, wherein transferring the at least one recurring charge fromthe first account to the second account comprises:

accessing, by the at least one computing processor, an account of amerchant associated with the at least one recurring charge using themerchant-related credentials, and instructing the merchant to charge inthe future the at least one recurring charge to the second account.

Clause 6. The method of clause 1 or any embodiment of the presentdisclosure, wherein the account credentials associated with the firstaccount include a username and password for the first account.Clause 7. The method of clause 1 or any embodiment of the presentdisclosure, wherein the merchant-related credentials associated with theat least one recurring charge include a username and password for anaccount of a merchant associated with the at least one recurring charge.Clause 8. The method of clause 1 or any embodiment of the presentdisclosure, further comprising: displaying, by the at least onecomputing processor, a transfer status of the at least one recurringcharge.Clause 9. The method of clause 1 or any embodiment of the presentdisclosure, further comprising:

providing, by the at least one computing processor, a listing ofrecurring charges transferred from the first account to the secondaccount.

Clause 10. The method of clause 1 or any embodiment of the presentdisclosure, further comprising:

transferring, by the at least one computing processor, a balance fromthe first account to the second account.

Clause 11. A computer-implemented method comprising:

receiving, by at least one computing processor, a request from a user totransfer a balance from a first account of a first financial institutionto a second account of a second financial institution;

generating, by the at least one computing processor, a first userinterface that enables the user to provide account informationassociated with first account, wherein the account information comprises(i) a plurality of statements associated with the first account, (ii)account credentials associated with the first account, or both (i) and(ii);

determining, by the at least one computing processor and using theaccount information, at least one recurring transaction of the firstaccount;

generating, by the at least one computing processor, a second userinterface that (a) enables the user to submit merchant-relatedcredentials associated with the at least one recurring transaction, (b)provides a link to a landing page associated with the at least onerecurring transaction, or both (a) and (b); and

wherein the method further comprises:

transferring, by the at least one computing processor and using themerchant-related credentials, the at least one recurring transactionfrom the first account to the second account, or redirecting, by the atleast one computing processor, the user to the landing page at which theuser can login to transfer the at least one recurring transaction fromthe first account to the second account.

Clause 12. The method of clause 11 or any embodiment of the presentdisclosure, wherein determining the at least one recurring transactionis based on the plurality of statements.Clause 13. The method of clause 11 or any embodiment of the presentdisclosure, wherein determining the at least one recurring transactionincludes accessing, by the at least one computing processor, informationabout a plurality of transactions of the first account using the accountcredentials, and determining the at least one recurring transactionbased on the information about the plurality of transactions.Clause 14. The method of clause 11 or any embodiment of the presentdisclosure, wherein transferring the at least one recurring transactionfrom the first account to the second account comprises:accessing, by the at least one computing processor, an account of amerchant associated with the at least one recurring transaction usingthe merchant-related credentials, and instructing the merchant to use inthe future the second account for the recurring transaction.Clause 15. The method of clause 11 or any embodiment of the presentdisclosure, wherein the account credentials associated with the firstaccount include a username and password for the first account.Clause 16. The method of clause 1 or any embodiment of the presentdisclosure, wherein the merchant-related credentials associated with theat least one recurring transaction include a username and password foran account of a merchant associated with the at least one recurringtransaction.Clause 17. The method of clause 11 or any embodiment of the presentdisclosure, further comprising:

displaying, by the at least one computing processor, a transfer statusof the at least one recurring transaction.

Clause 18. The method of clause 11 or any embodiment of the presentdisclosure, further comprising:

providing, by the at least one computing processor, a listing ofrecurring transactions transferred from the first account to the secondaccount.

Clause 19. The method of clause 11 or any embodiment of the presentdisclosure, further comprising:

transferring, by the at least one computing processor, the balance fromthe first account to the second account.

Clause 20. A computer-implemented method comprising:

receiving, by at least one computing processor, a request from a user totransfer a balance from a first account of a first financial institutionto a second account of a second financial institution;

generating, by the at least one computing processor, a first userinterface that enables the user to provide a plurality of statementsassociated with the first account and account credentials associatedwith the first account;

determining, by the at least one computing processor and using theplurality of statements or the account information, at least onerecurring transaction among a plurality of transactions of the firstaccount;

generating, by the at least one computing processor, a second userinterface that enables the user to submit merchant-related credentialsassociated with the at least one recurring transaction, and provides alink to a landing page associated with the at least one recurringtransaction; and

wherein the method further comprises:

transferring, by the at least one computing processor and using themerchant-related credentials, the at least one recurring transactionfrom the first account to the second account, or redirecting, by the atleast one computing processor, the user to the landing page at which theuser can login to transfer the at least one recurring transaction fromthe first account to the second account.

Clause 21. Embodiments herein may also take the form of a systemcomprised of computing elements that are arranged, coupled, configured,programmed and/or otherwise adapted to perform the features andfunctionality set forth anywhere in the present disclosure.Clause 22. In addition, embodiments herein may also take the form of oneor more computer readable media containing computer-executableinstructions for performing any of the processing herein, thecomputer-executable instructions being executable via one or moreprocessing components to process instructions regarding and/or otherwiseperform one or more aspects of the functionality set forth herein.

While one or more embodiments of the present disclosure have beendescribed, it is understood that these embodiments are illustrativeonly, and not restrictive, and that many modifications may becomeapparent to those of ordinary skill in the art, including that variousembodiments of the inventive methodologies, the inventivesystems/platforms, and the inventive devices described herein can beutilized in any combination with each other. Further still, the varioussteps may be carried out in any desired order (and any desired steps maybe added and/or any desired steps may be eliminated).

1. A computer-implemented method comprising: receiving, by at least onecomputing processor, a request from a user to transfer recurring chargesfrom a first account of a first financial institution to a secondaccount of a second financial institution; generating, by the at leastone computing processor, a first user interface that enables the user toprovide account information associated with first account, wherein theaccount information comprises (i) a plurality of statements associatedwith the first account, (ii) account credentials associated with thefirst account, or both (i) and (ii); determining, by the at least onecomputing processor and using the account information, at least onerecurring charge of the first account; generating, by the at least onecomputing processor, a second user interface that is configured to: (i)display to the user the at least one recurring charge, and (ii) promptthe user to submit merchant-related credentials associated with the atleast one recurring charge; and transferring, by the at least onecomputing processor and using the merchant-related credentials, the atleast one recurring charge from the first account to the second account.2. The method of claim 1, wherein determining the at least one recurringcharge is based on the plurality of statements.
 3. The method of claim1, wherein determining the at least one recurring charge includesaccessing, by the at least one computing processor, information about aplurality of charges of the first account using the account credentials,and determining the at least one recurring charge based on theinformation about the plurality of charges.
 4. The method of claim 1,wherein transferring the at least one recurring charge from the firstaccount to the second account comprises: instructing, by the at leastone computing processor and using the merchant-related credentials, amerchant associated with the at least one recurring charge to charge inthe future the at least one recurring charge to the second account. 5.The method of claim 1, wherein transferring the at least one recurringcharge from the first account to the second account comprises:accessing, by the at least one computing processor, an account of amerchant associated with the at least one recurring charge using themerchant-related credentials, and instructing the merchant to charge inthe future the at least one recurring charge to the second account. 6.The method of claim 1, wherein the account credentials associated withthe first account include a username and password for the first account.7. The method of claim 1, wherein the merchant-related credentialsassociated with the at least one recurring charge include a username andpassword for an account of a merchant associated with the at least onerecurring charge.
 8. The method of claim 1, further comprising:displaying, by the at least one computing processor, a transfer statusof the at least one recurring charge.
 9. The method of claim 1, furthercomprising: providing, by the at least one computing processor, alisting of recurring charges transferred from the first account to thesecond account.
 10. The method of claim 1, further comprising:transferring, by the at least one computing processor, a balance fromthe first account to the second account.
 11. A computer-implementedmethod comprising: receiving, by at least one computing processor, arequest from a user to transfer a balance from a first account of afirst financial institution to a second account of a second financialinstitution; generating, by the at least one computing processor, afirst user interface that enables the user to provide accountinformation associated with first account, wherein the accountinformation comprises (i) a plurality of statements associated with thefirst account, (ii) account credentials associated with the firstaccount, or both (i) and (ii); determining, by the at least onecomputing processor and using the account information, at least onerecurring transaction of the first account; generating, by the at leastone computing processor, a second user interface that (a) enables theuser to submit merchant-related credentials associated with the at leastone recurring transaction, (b) provides a link to a landing pageassociated with the at least one recurring transaction, or both (a) and(b); and wherein the method further comprises: transferring, by the atleast one computing processor and using the merchant-relatedcredentials, the at least one recurring transaction from the firstaccount to the second account, or redirecting, by the at least onecomputing processor, the user to the landing page at which the user canlogin to transfer the at least one recurring transaction from the firstaccount to the second account.
 12. The method of claim 11, whereindetermining the at least one recurring transaction is based on theplurality of statements.
 13. The method of claim 11, wherein determiningthe at least one recurring transaction includes accessing, by the atleast one computing processor, information about a plurality oftransactions of the first account using the account credentials, anddetermining the at least one recurring transaction based on theinformation about the plurality of transactions.
 14. The method of claim11, wherein transferring the at least one recurring transaction from thefirst account to the second account comprises: accessing, by the atleast one computing processor, an account of a merchant associated withthe at least one recurring transaction using the merchant-relatedcredentials, and instructing the merchant to use in the future thesecond account for the recurring transaction.
 15. The method of claim11, wherein the account credentials associated with the first accountinclude a username and password for the first account.
 16. The method ofclaim 11, wherein the merchant-related credentials associated with theat least one recurring transaction include a username and password foran account of a merchant associated with the at least one recurringtransaction.
 17. The method of claim 11, further comprising: displaying,by the at least one computing processor, a transfer status of the atleast one recurring transaction.
 18. The method of claim 11, furthercomprising: providing, by the at least one computing processor, alisting of recurring transactions transferred from the first account tothe second account.
 19. The method of claim 11, further comprising:transferring, by the at least one computing processor, the balance fromthe first account to the second account.
 20. A computer-implementedmethod comprising: receiving, by at least one computing processor, arequest from a user to transfer a balance from a first account of afirst financial institution to a second account of a second financialinstitution; generating, by the at least one computing processor, afirst user interface that enables the user to provide a plurality ofstatements associated with the first account and account credentialsassociated with the first account; determining, by the at least onecomputing processor and using the plurality of statements or the accountinformation, at least one recurring transaction among a plurality oftransactions of the first account; generating, by the at least onecomputing processor, a second user interface that enables the user tosubmit merchant-related credentials associated with the at least onerecurring transaction, and provides a link to a landing page associatedwith the at least one recurring transaction; and wherein the methodfurther comprises: transferring, by the at least one computing processorand using the merchant-related credentials, the at least one recurringtransaction from the first account to the second account, orredirecting, by the at least one computing processor, the user to thelanding page at which the user can login to transfer the at least onerecurring transaction from the first account to the second account.